| 21 Oct 2021 |
|  vieira#5145 changed their profile picture. | 21:20:44 |
| 22 Oct 2021 |
|  awesome enjoyer joined the room. | 01:24:36 |
 mattplm | In reply to @mattplm:matrix.org
Hey, question to awesome devs. How do you go about setting up your dev/testing environment ? I always get errors when running the integration tests. I think I installed everything listed here https://awesomewm.org/apidoc/documentation/10-building-and-testing.md.html and have no problem compiling the project. Trace : https://hastebin.com/pesixikayo.sh (assertion error on test-awful-tag.lua is mine). * I'm on debian 11 btw, probably worth mentioning | 13:14:22 |
|  Yes1 changed their display name from Yes1 to QUACK#3122. | 13:24:03 |
| Yes1 changed their display name from QUACK#3122 to Yes1. | 13:24:04 |
|  Everforest aficionado changed their display name from Everforest aficionado to Theory_of_Everything#4163. | 16:15:16 |
| Everforest aficionado changed their display name from Theory_of_Everything#4163 to Everforest aficionado. | 16:15:17 |
|  titof2375 joined the room. | 17:19:49 |
| awesome enjoyer changed their display name from MURICA_ENJOYER to MURICA_ENJOYER#7187. | 19:19:35 |
| awesome enjoyer changed their display name from MURICA_ENJOYER#7187 to awesome enjoyer. | 19:19:36 |
|  Bran changed their display name from Bran to Bran#6396. | 19:29:50 |
| Bran changed their display name from Bran#6396 to Bran. | 19:29:52 |
| Bran changed their display name from Bran to Bran#6396. | 19:57:47 |
| Bran changed their display name from Bran#6396 to Bran. | 19:57:48 |
|  Atreo joined the room. | 20:47:54 |
|  Aquinary joined the room. | 22:09:04 |
| 23 Oct 2021 |
|  SamEricEdge joined the room. | 07:54:23 |
| Bran changed their display name from Bran to Bran#6396. | 09:32:58 |
| Bran changed their display name from Bran#6396 to Bran. | 09:33:01 |
|  Scisista joined the room. | 11:27:40 |
|  nuxsh changed their display name from nuxsh to nuxsh#9338. | 13:25:13 |
| nuxsh changed their display name from nuxsh#9338 to nuxsh. | 13:25:19 |
 aire-one | In reply to @mattplm:matrix.org
Hey, question to awesome devs. How do you go about setting up your dev/testing environment ? I always get errors when running the integration tests. I think I installed everything listed here https://awesomewm.org/apidoc/documentation/10-building-and-testing.md.html and have no problem compiling the project. Trace : https://hastebin.com/pesixikayo.sh (assertion error on test-awful-tag.lua is mine). Sorry for the delay before checking in.
Can you try to restart the test multiple times to see if you still have issues. It seems most of them are basically timing issues. So maybe they are "random" and happen because of luck or because you have low end hardware?
If it persists, please open an issue on github. | 13:29:31 |
| aire-one | the test-screenshot fail is expected. we merged the fix only yesterday | 13:30:21 |
| aire-one | * the test-screenshot fail is expected. we merged the fix only yesterday | 13:30:37 |
| Yes1 changed their display name from Yes1 to QUACK#3122. | 14:01:25 |
| Yes1 changed their display name from QUACK#3122 to Yes1. | 14:01:26 |
| mattplm | Hey thanks for the reply. I just merged your master and test-screenshot passes now. test-input-binding has disapeared too but it was kind of random in the previous days so I'll keep an eye on it.
About the other errors, I'm assuming we're looking at those :
stack traceback:
/home/matt/repos/awesome/tests/test-dpi.lua:293: in function </home/matt/repos/awesome/tests/test-dpi.lua:291>
(...tail calls...)
[C]: in function 'xpcall'
/home/matt/repos/awesome/tests/_runner.lua:110: in function </home/matt/repos/awesome/tests/_runner.lua:101>
[C]: in function 'xpcall'
lib/gears/protected_call.lua:36: in function <lib/gears/protected_call.lua:35>
(...tail calls...)
lib/gears/timer.lua:255: in function 'gears.timer.run_delayed_calls_now'
# And
Error: failed to wait for X clients from previous test to close!
Last reply: .
[...]
Maybe you've figured something out about my hardware. I have what used to be a somewhat decent thinkpad, but it is starting to show some signs of decline so it could be it. I should try my other PC someday. But they are not random, they happen every run. If I manage to run the test suite elsewhere and still get those I'll open an issue. For now, I'll assume my PC is the culprit.
| 14:38:50 |
| mattplm | * Hey thanks for the reply. I just merged your master and test-screenshot passes now. test-input-binding has disapeared too but it was kind of random in the previous days so I'll keep an eye on it.
About the other errors, I'm assuming we're looking at those :
stack traceback:
/home/matt/repos/awesome/tests/test-dpi.lua:293: in function </home/matt/repos/awesome/tests/test-dpi.lua:291>
(...tail calls...)
[C]: in function 'xpcall'
/home/matt/repos/awesome/tests/_runner.lua:110: in function </home/matt/repos/awesome/tests/_runner.lua:101>
[C]: in function 'xpcall'
lib/gears/protected_call.lua:36: in function <lib/gears/protected_call.lua:35>
(...tail calls...)
lib/gears/timer.lua:255: in function 'gears.timer.run_delayed_calls_now'
# And
Error: failed to wait for X clients from previous test to close!
Last reply: .
[...]
Maybe you've figured something out about my hardware. I have what used to be a somewhat decent thinkpad, but it is starting to show some signs of decline so it could be it. I should try my other PC someday. But they are not random, they happen every run. If I manage to run the test suite elsewhere and still get those I'll open an issue. For now, I'll assume my PC is the culprit.
| 14:39:32 |
 SirAiedail | If you look at the line above those stack traces, you'll notice that they're flagged with a severity of "warning"(W:). They're not errors.
s:fake_remove() should be avoided in regular users configs, hence the verbose warning, but the tests do make use of that method when needed. | 14:43:01 |
