| Time |
Nick |
Message |
| 02:17 |
|
dreuther_ joined #evergreen |
| 03:13 |
|
mceraso joined #evergreen |
| 04:56 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 05:55 |
|
zerick joined #evergreen |
| 07:13 |
|
mceraso joined #evergreen |
| 07:16 |
csharp |
bshum: bug 1272937 |
| 07:16 |
pinesol_green |
Launchpad bug 1272937 in OpenSRF "OpenSRF configure.am showing deprecation warnings with autoreconf -i step" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1272937 |
| 07:23 |
bshum |
Aha |
| 07:23 |
bshum |
Special. |
| 07:41 |
bshum |
csharp++ # thanks for pointing me at the bug and corresponding thread discussions. You're right, they are... "colorful" |
| 08:06 |
|
ktomita joined #evergreen |
| 08:55 |
bshum |
csharp: For fun, I added some new commits in http://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/user/bshum/ubuntu-14-04-makefile to poke at some of the various errors from that thread. I have no idea what I'm doing, so it might all be wrong, but the errors are gone on subsequent runs. |
| 08:56 |
bshum |
*thread/bug |
| 08:57 |
bshum |
The m4 directory for macros is a bit controversial sounding though, from my googling. In the sense that the warning is something we should ignore and not fix. |
| 08:58 |
bshum |
Still researching. I'll look more at it later on. |
| 09:26 |
bshum |
Nope, that's not good. I'm leaving that libtoolize error alone for now since it's always been there. |
| 09:27 |
bshum |
But let's see how the other changes fly. Force pushed an updated branch to the repo |
| 13:12 |
|
ldwhalen joined #evergreen |
| 13:58 |
|
mtcarlson_away joined #evergreen |
| 14:27 |
|
mtcarlson_away joined #evergreen |
| 14:54 |
|
mtcarlson_away joined #evergreen |
| 14:54 |
|
mceraso joined #evergreen |
| 14:55 |
|
zerick joined #evergreen |
| 15:05 |
|
ldwhalen joined #evergreen |
| 15:26 |
|
mtcarlson_away joined #evergreen |
| 16:10 |
|
ldwhalen joined #evergreen |
| 17:18 |
gsams |
I'm having an issue, it appears a report is caught, but the normal method of softly killing it doesn't seem to work. |
| 17:19 |
gsams |
the report shows up in the currently_running view, but doesn't show up when I run the query against pg_stat_activity |
| 17:28 |
gsams |
mkay, deleting the report directly from the schedule seems to have done the trick for now |
| 21:13 |
|
mtcarlson_away joined #evergreen |
| 21:29 |
|
mtcarlson_away joined #evergreen |
