Your message dated Wed, 16 Nov 2022 12:33:22 +0500
with message-id <877czvical.fsf@localhost>
and subject line Close #1022253
has caused the Debian Bug report #1022253,
regarding swi-prolog breaks logol autopkgtest on s390x
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1022253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022253
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: swi-prolog, logol
Control: found -1 swi-prolog/8.4.3+dfsg-2
Control: found -1 logol/1.7.9+dfsg-5
Severity: serious
Tags: sid bookworm
User: [email protected]
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of swi-prolog the autopkgtest of logol fails in
testing when that autopkgtest is run with the binary packages of
swi-prolog from unstable. It passes when run with only packages from
testing. In tabular form:
pass fail
swi-prolog from testing 8.4.3+dfsg-2
logol from testing 1.7.9+dfsg-5
all others from testing from testing
I copied some of the output at the bottom of this report. I note that
the last changelog for swi-prolog mentions endianness, s390x is our only
big endian release architecture.
Currently this regression is blocking the migration of swi-prolog to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=swi-prolog
https://ci.debian.net/data/autopkgtest/testing/s390x/l/logol/27384041/log.gz
calling logol with parameters -g 1799.logol -s 1799.fasta -dna
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /var/log/logol/logol.log (Permission denied)
at java.base/java.io.FileOutputStream.open0(Native Method)
at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298)
at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:237)
at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:158)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
at
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
at
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
at
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
at
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
at
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
at
org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
at
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)
at org.apache.log4j.LogManager.<clinit>(LogManager.java:127)
at org.apache.log4j.Logger.getLogger(Logger.java:117)
at org.irisa.genouest.logol.Logol.<clinit>(Unknown Source)
For help, use option -h
INFO org.irisa.genouest.logol.Logol - Using configuration file:
/usr/share/logol/prolog/logol.properties
INFO org.irisa.genouest.logol.Logol - option g called with 1799.logol
INFO org.irisa.genouest.logol.Logol - option s called with 1799.fasta
INFO org.irisa.genouest.logol.Logol - No maximum solutions defined,
using defaults
INFO org.irisa.genouest.logol.Logol - option dna called
INFO org.irisa.genouest.logol.Logol - Start analyse to create grammar
analyser
Executing prolog for pre-analyse
java.io.FileNotFoundException:
/tmp/1799.logol.f7104ea4-749d-45b1-8375-321313c4c203.pre.res (No such
file or directory)
at java.base/java.io.FileInputStream.open0(Native Method)
at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
at java.base/java.io.FileInputStream.<init>(FileInputStream.java:157)
at java.base/java.io.FileReader.<init>(FileReader.java:75)
at org.irisa.genouest.logol.Logol.loadVariables2Postpone(Unknown Source)
at org.irisa.genouest.logol.Logol.generatePreAnalysis(Unknown Source)
at org.irisa.genouest.logol.Logol.analyse(Unknown Source)
at org.irisa.genouest.logol.Logol.execute(Unknown Source)
at org.irisa.genouest.logol.Logol.main(Unknown Source)
INFO org.irisa.genouest.logol.Logol - Analyse in progress..
WARN org.irisa.genouest.logol.SequenceAnalyser - Path to suffix search
tool is not set in system environment. Will try to execute directly but
may fail if not in PATH of current user
ERROR org.irisa.genouest.logol.SequenceAnalyser - Program exited with
wrong status code: 134
Exception in thread "main" org.irisa.genouest.logol.GrammarException:
ERROR: Coudld not execute program: Program exited with wrong status code
at org.irisa.genouest.logol.Logol.execute(Unknown Source)
at org.irisa.genouest.logol.Logol.main(Unknown Source)
autopkgtest [00:56:16]: test run-unit-test
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Since #1023890 is closed now, and logol on s390x passes tests
successfully, I'm closing this bug report.
Thanks!
Regards,
Lev
--- End Message ---
