Comments (3)
Good catch. I pushed five new tests for the right-most option taking precedence to the Logtalk git version. With the latest git version of GNU Prolog (204c41e), I get only a single failure (the one mentioned above:
$ logtalk_tester -p gnu
% Batch testing started @ 2023-06-29 23:56:26
% Logtalk version: 3.67.0-b02
% GNU Prolog version: 1.6.0
%
% Documents/Logtalk/logtalk3/tests/prolog/predicates/write_term_3
% 122 tests: 0 skipped, 121 passed, 1 failed (0 flaky)
% completed tests from object tests in 2 seconds
% clause coverage n/a
%
% Compilation errors/warnings and failed unit tests
% (compilation errors/warnings might be expected depending on the test)
! lgt_write_term_3_122: failure (in 0.0 seconds)
! test assertion failed: 'Used'=='Ignor'
! in file Documents/Logtalk/logtalk3/tests/prolog/predicates/write_term_3/tests.lgt between lines 659-662
%
% Failed tests
Documents/Logtalk/logtalk3/tests/prolog/predicates/write_term_3/tests.lgt - lgt_write_term_3_122 @ tests
%
% 1 test sets: 1 completed, 0 skipped, 0 broken, 0 timedout, 0 crashed
% 122 tests: 0 skipped, 121 passed, 1 failed (0 flaky)
%
% Batch testing ended @ 2023-06-29 23:56:29
``
from gprolog.
from gprolog.
Progress! Still #60 ff...
from gprolog.
Related Issues (20)
- Write option max_depth/1 differences HOT 29
- Leak with simple arithmetics HOT 4
- Power not defined HOT 1
- Linking error riscv64
- Problem processing repeated calls HOT 3
- New show_information flag regression HOT 1
- Typo in Load_Math_Expression?
- Insure project web site
- GNU Prolog Parser accepts incomplete clause.
- hand written C code lacks some garbage collection.
- real_file_name does not follow symlinks on Windows HOT 1
- numbervars/3 silently refuses to number vars
- ensure_loaded/1 wants suddently predicate indicator HOT 1
- Ubuntu defaults so that GNU compile result is speedy HOT 1
- Incorrect answers when exceeding domains
- phrase/2 too eager execution HOT 1
- Feature request: format_time
- Ma2Asm for linux x64 with gcc is not generating PIC code (v1.5.0+)
- GNU Prolog crashes when reading long string literals
- GNU Prolog segmentation faults when using read_term/3 on a huge file
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from gprolog.