| guruprasad | doko, that must be tsimonq2 based on what we found in #launchpad | 00:15 |
|---|---|---|
| tsimonq2 | doko, guruprasad, sudip: As I mentioned elsewhere last night, it's not all me and I've since stopped | 17:30 |
| tsimonq2 | Additionally, I haven't ran CI builds or anything overnight, and e.g. the riscv64 queue has barely budged. Is all this extra pinging and rescoring really worth the effort? | 17:31 |
| tsimonq2 | I am actually getting productive work done with the CI, and I definitely don't appreciate random re-scoring of my builds. | 17:32 |
| tsimonq2 | It blocks work, and in order for me to actually get the results I *need*, I need to do a whole new round of builds, which wastes resources generally speaking. | 17:33 |
| tsimonq2 | So yeah, I don't appreciate how one-sided this is. | 17:34 |
| tsimonq2 | Test rebuilds are useful, CI rebuilds are useful. They should stop fighting and be friends. | 17:34 |
| tsimonq2 | And just because someone has a stake in one over the other shouldn't give them the power to de-prioritize the other. That's why the builds haven't been constant. | 17:35 |
| tsimonq2 | I needed to work out some tooling, but that's done. If you actually plot out CI builds, they've done down exponentially since e.g. December or January. | 17:35 |
| tsimonq2 | So no, blindly rescoring isn't the answer. It's frustrating, and quite frankly, doesn't help anyone. | 17:36 |
| tsimonq2 | guruprasad, sudip: Explain this one to me... who's been rescoring all of the Lubuntu CI builds randomly? And who changed the build score setting in the PPA without talking to me? | 17:40 |
| === nishit_2 is now known as nishit_ | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!